Universal Access To All Knowledge
Home Donate | Store | Blog | FAQ | Jobs | Volunteer Positions | Contact | Bios | Forums | Projects | Terms, Privacy, & Copyright
Search: Advanced Search
Anonymous User (login or join us)
Upload

Reply to this post | Go Back
View Post [edit]

Poster: bradm Date: Aug 24, 2007 7:21am
Forum: etree Subject: Submission went waiting for admin, but why?

I uploaded a recording last night

http://www.archive.org/details/wc2003-06-12.sp-bmc3.shnf

and the transfer finished about 9:30pm (EDT), after which I went through the usual thing of filling out the forms and submitting it. I checked the status a minute or so later, and it looked good, but then went red ("waiting for admin"). I figured something had gone wrong during the transfer and the checksum check had failed, so I checked my e-mail, but there was nothing; I waited about 10 minutes, but no notice came through, so I went to bed.

This morning, I checked, and the show looks fine. Why did it go red, and then get processed fully? (And when a submission is waiting for admin, is there any way to check _why_ it's waiting for admin?)

Thanks,
Brad

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or StaffTyler Date: Aug 24, 2007 10:33am
Forum: etree Subject: Re: Submission went waiting for admin, but why?

"This morning, I checked, and the show looks fine. Why did it go red, and then get processed fully?"

It looks fine, I do not know why it would have failed. It looks 'all good'.

"when a submission is waiting for admin, is there any way to check _why_ it's waiting for admin?"

yes, you should get an e-mail saying why. But if it gets lost in your spam filter or something, click on the show, then 'item history'

http://www.archive.org/catalog.php?history=1&identifier=wc2003-06-12.sp-bmc3.shnf

Then under 'task ID' click the number that is the red row. it will be the 'derive.php' task. this is the correctly ran derive.php page for your show:

http://www.us.archive.org/log_show.php?task_id=18335964

in there will be a lot of info, but if you scroll to the very bottom, you'll see the end message from the system on what files failed md5 so you know what to fix.

thanks for uploading! Weird that it was red for a moment, but it looks all good now..

Reply to this post
Reply [edit]

Poster: bradm Date: Aug 24, 2007 10:38am
Forum: etree Subject: Re: Submission went waiting for admin, but why?

Thanks! I think the problem is actually detailed at the _start_ of the history, the first block of which ends with:

-----
df /dev/hd* /dev/sd* | grep "/[0-3]" | wc -l
3
FATAL ERROR: Node has less than 4 disks mounted. Stop doing anything.
df: `/dev/hd*': No such file or directory
-----

About 20 minutes later it tried that again, and got "4" instead of "3" as the result, so went ahead with the deriving (and all of the checksums passed). (Also, I use Yahoo! mail, which dumps anything that it thinks it spam into a "Bulk" folder, so I still see it; in this case, though, I didn't receive anything at all when it waiting for admin.)

Aloha,
Brad

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or StaffTyler Date: Aug 24, 2007 12:40pm
Forum: etree Subject: Re: Submission went waiting for admin, but why?

so it sounds like your case was a temp problem on the archive.org server sides that fixed itself.